Skip to content

qcom-multimedia-image: keep FastCV away from the image#151

Draft
lumag wants to merge 1 commit intoqualcomm-linux:mainfrom
lumag:no-fastcv
Draft

qcom-multimedia-image: keep FastCV away from the image#151
lumag wants to merge 1 commit intoqualcomm-linux:mainfrom
lumag:no-fastcv

Conversation

@lumag
Copy link
Contributor

@lumag lumag commented Feb 8, 2026

FastCV is not open-source, prevent it from being installed into the supposedly open-source image.

FastCV is not open-source, prevent it from being installed into the
supposedly open-source image.

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
@lumag lumag marked this pull request as draft February 8, 2026 21:43
@lumag
Copy link
Contributor Author

lumag commented Feb 8, 2026

Draft, it depends on the patch

@koenkooi
Copy link
Contributor

koenkooi commented Feb 9, 2026

Too bad we can't use wildcards, it looks good to me so far.

@lumag lumag marked this pull request as ready for review February 16, 2026 23:50
@sssanjee
Copy link

Hi @lumag , Does this change mean fastcv libs won't be part of qcom-multimedia-image ? . Also , does this impact qcom-multimedia-proprietary-image ? , asking since we do "require qcom-multimedia-image.bb" in https://github.com/qualcomm-linux/meta-qcom-distro/blob/main/recipes-products/images/qcom-multimedia-proprietary-image.bb

@lumag
Copy link
Contributor Author

lumag commented Feb 18, 2026

Hi @lumag , Does this change mean fastcv libs won't be part of qcom-multimedia-image ? .

Yes, it should not. It's closed source.

Also , does this impact qcom-multimedia-proprietary-image ? , asking since we do "require qcom-multimedia-image.bb" in https://github.com/qualcomm-linux/meta-qcom-distro/blob/main/recipes-products/images/qcom-multimedia-proprietary-image.bb

Ouch. I'll need to fix it.

@lumag lumag marked this pull request as draft February 18, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments